Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-12160][MLLIB] Use SQLContext.getOrCreate in MLlib - 1.5 backport #10183

Closed

Conversation

jkbradley
Copy link
Member

This backports [https://github.com//pull/10161] to Spark 1.5, with the difference that ChiSqSelector does not require modification.

Switched from using SQLContext constructor to using getOrCreate, mainly in model save/load methods.

This covers all instances in spark.mllib. There were no uses of the constructor in spark.ml.

CC: @yhuai @mengxr

Switched from using SQLContext constructor to using getOrCreate, mainly in model save/load methods.

This covers all instances in spark.mllib.  There were no uses of the constructor in spark.ml.

CC: mengxr yhuai

Author: Joseph K. Bradley <[email protected]>

Closes apache#10161 from jkbradley/mllib-sqlcontext-fix.

Conflicts:
	mllib/src/main/scala/org/apache/spark/mllib/feature/ChiSqSelector.scala
@SparkQA
Copy link

SparkQA commented Dec 8, 2015

Test build #47295 has finished for PR 10183 at commit acf1e55.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

asfgit pushed a commit that referenced this pull request Dec 8, 2015
This backports [#10161] to Spark 1.5, with the difference that ChiSqSelector does not require modification.

Switched from using SQLContext constructor to using getOrCreate, mainly in model save/load methods.

This covers all instances in spark.mllib. There were no uses of the constructor in spark.ml.

CC: yhuai mengxr

Author: Joseph K. Bradley <[email protected]>

Closes #10183 from jkbradley/sqlcontext-backport1.5.
@mengxr
Copy link
Contributor

mengxr commented Dec 8, 2015

LGTM. Merged into branch-1.5. Could you close this PR manually? Thanks!

@jkbradley jkbradley closed this Dec 8, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants